Skip to content

ci: publish EverMe to the MCP Registry - #24

Merged
cyfyifanchen merged 1 commit into
mainfrom
ci/publish-everme-mcp-registry
Nov 4, 2026
Merged

cyfyifanchen merged 1 commit into
mainfrom
ci/publish-everme-mcp-registry

Conversation

@cyfyifanchen

Copy link
Copy Markdown
Contributor

Summary

List the hosted EverMe MCP endpoint in the official MCP Registry. Merging this PR to main triggers publication under the EverMind-AI GitHub namespace using GitHub Actions OIDC.

Changes

  • Describe the Streamable HTTP endpoint in server.json using the current memory-mcp package version (0.6.1).
  • Publish on manifest changes to main, with a manual retry on main. Verify the pinned publisher binary against its release digest.

Test Plan

  • Validated server.json with the official registry schema and checked the staged diff for whitespace errors.
  • An unauthenticated initialize request returned HTTP 401 with a Bearer resource metadata challenge. Authenticated tool calls and registry publication have not been tested.
  • No CLI or plugin source changes. Go checks could not run locally because Go is unavailable. npm ci reported five moderate and two high audit findings in the existing dependency tree.

Security

  • No credentials, cookies, private URLs, or production logs included.

Related Issues

  • None

@gloryfromca gloryfromca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blockers; this can merge as far as I am concerned.

Reviewed the actual origin/main...HEAD delta after refreshing the stale local base ref. I covered the repository instructions, both added files, the hosted MCP caller/endpoint contract, relevant release and registry history, backward compatibility, test-strengthening/weakening, and the documented MCP naming/tool architecture constraints.

Validation performed:

  • mcp-publisher 1.8.7 validate: passed against the live registry.
  • Pinned publisher release and SHA-256: matched the official v1.8.7 asset.
  • Hosted /mcp probe: returned the expected OAuth protected-resource challenge.
  • Plugin workspace tests: passed (all workspaces).
  • npm audit --audit-level=moderate: failed on 7 existing dependency advisories (5 moderate, 2 high); this PR does not change dependency manifests or the lockfile, and the same failure is visible in PR CI.
  • Local CLI checks: not runnable because this environment has no Go toolchain; the PR's cli-test, fast gate, coverage, package smoke, and plugin test jobs passed.
  • git diff --check: passed; worktree restored clean after test-generated output.

The current failing aggregate CI result is solely the pre-existing dependency audit gate, not a defect introduced by this two-file change.

@cyfyifanchen
cyfyifanchen merged commit 2734785 into main Nov 4, 2026
5 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants